System for deployable software vulnerability testing platform

ABSTRACT

Systems, computer program products, and methods are described herein for deployable software vulnerability testing platform. The present invention is configured to receive, from a user input device, an initial request from a user to generate a deployable software vulnerability testing (SVT) engine; prompt an SVT dashboard for display on the user input device to receive one or more input parameters associated with the first vulnerability in response to receiving the initial request; receive, via the SVT dashboard, the one or more input parameters; generate the SVT engine based on at least the one or more input parameters; receive, from the user input device, one or more deployment parameters associated with a deployment of the SVT engine; and deploy the SVT engine within the distributed technology infrastructure to identify the one or more instances of the first vulnerability based on at least the one or more deployment parameters.

FIELD OF THE INVENTION

The present invention embraces a system for deployable softwarevulnerability testing platform.

BACKGROUND

In larger entities, many third party software applications are employedin the technology infrastructure to process information on a dailybasis. Each application is used to execute specific action. Mostentities have a record of the type of applications being used within thetechnology infrastructure. However, entities may not know information ata level of granularity that will allow for identification of specificlibraries that are depended upon by the applications to execute actions.

Therefore, there is a need for a deployable software vulnerabilitytesting platform capable of deploying a platform agnostic vulnerabilitytesting engine to identify the vulnerability quickly.

SUMMARY

The following presents a simplified summary of one or more embodimentsof the present invention, in order to provide a basic understanding ofsuch embodiments. This summary is not an extensive overview of allcontemplated embodiments and is intended to neither identify key orcritical elements of all embodiments nor delineate the scope of any orall embodiments. Its sole purpose is to present some concepts of one ormore embodiments of the present invention in a simplified form as aprelude to the more detailed description that is presented later.

In one aspect, a system for deployable software vulnerability testingplatform is presented. The system comprising: at least onenon-transitory storage device; and at least one processor coupled to theat least one non-transitory storage device, wherein the at least oneprocessor is configured to: receive, from a user input device, aninitial request from a user to generate a deployable softwarevulnerability testing (SVT) engine to identify one or more instances ofa first vulnerability within a distributed technology infrastructure;prompt an SVT dashboard for display on the user input device to receiveone or more input parameters associated with the first vulnerability inresponse to receiving the initial request; receive, via the SVTdashboard, the one or more input parameters; generate the SVT enginebased on at least the one or more input parameters; receive, from theuser input device, one or more deployment parameters associated with adeployment of the SVT engine; and deploy the SVT engine within thedistributed technology infrastructure to identify the one or moreinstances of the first vulnerability based on at least the one or moredeployment parameters.

In some embodiments, the SVT engine is platform agnostic.

In some embodiments, the at least one processor is further configuredto: receive, via the SVT dashboard, the one or more deploymentparameters, wherein the one or more deployment parameters comprises atleast information associated a first set of applications within thedistributed technology infrastructure; and deploy the SVT engine toidentify the one or more instances of the first vulnerability within thefirst set of applications within the distributed technologyinfrastructure.

In some embodiments, the information associated with the first set ofapplications comprises at least an application version.

In some embodiments, the at least one processor is further configuredto: receive, via the SVT dashboard, the one or more deploymentparameters, wherein the one or more deployment parameters comprises atleast information associated with one or more software libraries;determine a second set of applications that are associated with the oneor more software libraries; and deploy the SVT engine to identify theone or more instances of the first vulnerability within the second setof applications within the distributed technology infrastructure.

In some embodiments, the one or more input parameters comprises at leastinformation associated with the first vulnerability, wherein theinformation comprises at least one or more known vulnerabilitysignatures associated with the first vulnerability.

In some embodiments, the at least one processor is further configuredto: receive, from the user input device, one or more actions to beexecuted in response to identifying the one or more instances of thefirst vulnerability within the distributed technology infrastructure;and store the one or more actions in an action repository.

In some embodiments, the one or more actions comprises at least asoftware patch configured to address the first vulnerability in the oneor more instances identified.

In some embodiments, the at least one processor is further configuredto: identify the one or more instances of the first vulnerability withinthe distributed technology infrastructure based on at least deployingthe SVT engine within the distributed technology infrastructure;automatically retrieve, from the action repository, the one or moreactions in response to identifying the one or more instances of thefirst vulnerability; and executing the one or more actions on the firstvulnerability in the one or more instances identified.

In another aspect, a computer program product for deployable softwarevulnerability testing platform is presented. The computer programproduct comprising a non-transitory computer-readable medium comprisingcode causing a first apparatus to: receive, from a user input device, aninitial request from a user to generate a deployable softwarevulnerability testing (SVT) engine to identify one or more instances ofa first vulnerability within a distributed technology infrastructure;prompt an SVT dashboard for display on the user input device to receiveone or more input parameters associated with the first vulnerability inresponse to receiving the initial request; receive, via the SVTdashboard, the one or more input parameters; generate the SVT enginebased on at least the one or more input parameters; receive, from theuser input device, one or more deployment parameters associated with adeployment of the SVT engine; and deploy the SVT engine within thedistributed technology infrastructure to identify the one or moreinstances of the first vulnerability based on at least the one or moredeployment parameters.

In yet another aspect, a method for deployable software vulnerabilitytesting platform is presented. The method comprising: receiving, from auser input device, an initial request from a user to generate adeployable software vulnerability testing (SVT) engine to identify oneor more instances of a first vulnerability within a distributedtechnology infrastructure; prompting an SVT dashboard for display on theuser input device to receive one or more input parameters associatedwith the first vulnerability in response to receiving the initialrequest; receiving, via the SVT dashboard, the one or more inputparameters; generating the SVT engine based on at least the one or moreinput parameters; receiving, from the user input device, one or moredeployment parameters associated with a deployment of the SVT engine;and deploying the SVT engine within the distributed technologyinfrastructure to identify the one or more instances of the firstvulnerability based on at least the one or more deployment parameters.

The features, functions, and advantages that have been discussed may beachieved independently in various embodiments of the present inventionor may be combined with yet other embodiments, further details of whichcan be seen with reference to the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made the accompanying drawings, wherein:

FIG. 1 illustrates technical components of a system for deployablesoftware vulnerability testing platform, in accordance with anembodiment of the invention;

FIG. 2 illustrates a process flow for deployable software vulnerabilitytesting platform, in accordance with an embodiment of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Where possible, any terms expressed in the singularform herein are meant to also include the plural form and vice versa,unless explicitly stated otherwise. Also, as used herein, the term “a”and/or “an” shall mean “one or more,” even though the phrase “one ormore” is also used herein. Furthermore, when it is said herein thatsomething is “based on” something else, it may be based on one or moreother things as well. In other words, unless expressly indicatedotherwise, as used herein “based on” means “based at least in part on”or “based at least partially on.” Like numbers refer to like elementsthroughout.

As used herein, an “entity” may be any institution employing informationtechnology resources and particularly technology infrastructureconfigured for processing large amounts of data. Typically, these datacan be related to the people who work for the organization, its productsor services, the customers or any other aspect of the operations of theorganization. As such, the entity may be any institution, group,association, financial institution, establishment, company, union,authority or the like, employing information technology resources forprocessing large amounts of data.

As described herein, a “user” may be an individual associated with anentity. As such, in some embodiments, the user may be an individualhaving past relationships, current relationships or potential futurerelationships with an entity. In some embodiments, a “user” may be anemployee (e.g., an associate, a project manager, an IT specialist, amanager, an administrator, an internal operations analyst, or the like)of the entity or enterprises affiliated with the entity, capable ofoperating the systems described herein. In some embodiments, a “user”may be any individual, entity or system who has a relationship with theentity, such as a customer or a prospective customer. In otherembodiments, a user may be a system performing one or more tasksdescribed herein.

As used herein, a “user interface” may be any device or software thatallows a user to input information, such as commands or data, into adevice, or that allows the device to output information to the user. Forexample, the user interface includes a graphical user interface (GUI) oran interface to input computer-executable instructions that direct aprocessor to carry out specific functions. The user interface typicallyemploys certain input and output devices to input data received from auser second user or output data to a user. These input and outputdevices may include a display, mouse, keyboard, button, touchpad, touchscreen, microphone, speaker, LED, light, joystick, switch, buzzer, bell,and/or other user input/output device for communicating with one or moreusers.

As used herein, an “engine” may refer to core elements of anapplication, or part of an application that serves as a foundation for alarger piece of software and drives the functionality of the software.In some embodiments, an engine may be self-contained, butexternally-controllable code that encapsulates powerful logic designedto perform or execute a specific type of function. In one aspect, anengine may be underlying source code that establishes file hierarchy,input and output methods, and how a specific part of an applicationinteracts or communicates with other software and/or hardware. Thespecific components of an engine may vary based on the needs of thespecific application as part of the larger piece of software. In someembodiments, an engine may be configured to retrieve resources createdin other applications, which may then be ported into the engine for useduring specific operational aspects of the engine. An engine may beconfigurable to be implemented within any general purpose computingsystem. In doing so, the engine may be configured to execute source codeembedded therein to control specific features of the general purposecomputing system to execute specific computing operations, therebytransforming the general purpose system into a specific purposecomputing system.

As used herein, “authentication credentials” may be any information thatcan be used to identify of a user. For example, a system may prompt auser to enter authentication information such as a username, a password,a personal identification number (PIN), a passcode, biometricinformation (e.g., iris recognition, retina scans, fingerprints, fingerveins, palm veins, palm prints, digital bone anatomy/structure andpositioning (distal phalanges, intermediate phalanges, proximalphalanges, and the like), an answer to a security question, a uniqueintrinsic user activity, such as making a predefined motion with a userdevice. This authentication information may be used to authenticate theidentity of the user (e.g., determine that the authenticationinformation is associated with the account) and determine that the userhas authority to access an account or system. In some embodiments, thesystem may be owned or operated by an entity. In such embodiments, theentity may employ additional computer systems, such as authenticationservers, to validate and certify resources inputted by the plurality ofusers within the system. The system may further use its authenticationservers to certify the identity of users of the system, such that otherusers may verify the identity of the certified users. In someembodiments, the entity may certify the identity of the users.Furthermore, authentication information or permission may be assigned toor required from a user, application, computing node, computing cluster,or the like to access stored data within at least a portion of thesystem.

It should also be understood that “operatively coupled,” as used herein,means that the components may be formed integrally with each other, ormay be formed separately and coupled together. Furthermore, “operativelycoupled” means that the components may be formed directly to each other,or to each other with one or more components located between thecomponents that are operatively coupled together. Furthermore,“operatively coupled” may mean that the components are detachable fromeach other, or that they are permanently coupled together. Furthermore,operatively coupled components may mean that the components retain atleast some freedom of movement in one or more directions or may berotated about an axis (i.e., rotationally coupled, pivotally coupled).Furthermore, “operatively coupled” may mean that components may beelectronically connected and/or in fluid communication with one another.

As used herein, an “interaction” may refer to any communication betweenone or more users, one or more entities or institutions, and/or one ormore devices, nodes, clusters, or systems within the system environmentdescribed herein. For example, an interaction may refer to a transfer ofdata between devices, an accessing of stored data by one or more nodesof a computing cluster, a transmission of a requested task, or the like.

As used herein, “determining” may encompass a variety of actions. Forexample, “determining” may include calculating, computing, processing,deriving, investigating, ascertaining, and/or the like. Furthermore,“determining” may also include receiving (e.g., receiving information),accessing (e.g., accessing data in a memory), and/or the like. Also,“determining” may include resolving, selecting, choosing, calculating,establishing, and/or the like. Determining may also include ascertainingthat a parameter matches a predetermined criterion, including that athreshold has been met, passed, exceeded, and so on.

In larger entities, many third party software applications are employedin the technology infrastructure to process information on a dailybasis. Each application is used to execute specific action. Mostentities have a record of the type of applications being used within thetechnology infrastructure. However, entities may not know information ata level of granularity that will allow for identification of specificlibraries that are depended upon by the applications to execute actions.It is not uncommon for certain applications to depend on third partylibraries to perform specific actions. During ingestion of a newtechnology (e.g., application), most entities do not itemize the list oflibraries associated with that technology. Entities often employsecurity tools to monitor the technology infrastructure forvulnerabilities. While most security tools identify vulnerabilities witha specific software, they do not have the capability to identifylibrary-level vulnerabilities in the software.

This present invention proposes a platform (e.g., operating system)agnostic deployable vulnerability testing engine that may be configuredto identify a particular vulnerability in applications across thetechnology infrastructure. To configure the engine to identify theparticular vulnerability, the concept proposes defining a set ofvectors. The vectors may define where to look, what to look for, andwhat to do when the vulnerability is found. In one example, thevulnerability may have been identified by the entity in a particularlibrary (e.g., Log4 j) that is used in many software applications acrossthe technology infrastructure. In cases where the entity does not knowthe specific applications that depend on that library for operation, thevectors may be used to define the specific library where thevulnerability was found, version of the application with that library,unique signature of the vulnerability, and actions to execute if thevulnerability is identified. In some embodiments, the present inventionallows for deployment of a number of such engines on short notice toidentify the vulnerability quickly instead of having to depend on thedevelopers of the third party vulnerability tool to update the vectorsto identify the vulnerability.

FIG. 1 illustrates technical components of a system for deployablesoftware vulnerability testing platform 100, in accordance with anembodiment of the invention. FIG. 1 provides a unique system thatincludes specialized servers and system communicably linked across adistributive network of nodes required to perform the functions of theprocess flows described herein in accordance with embodiments of thepresent invention.

As illustrated, the system environment 100 includes a network 110, asystem 130, and a user input device 140. In some embodiments, the system130, and the user input device 140 may be used to implement theprocesses described herein, in accordance with an embodiment of thepresent invention. In this regard, the system 130 and/or the user inputdevice 140 may include one or more applications stored thereon that areconfigured to interact with one another to implement any one or moreportions of the various user interfaces and/or process flow describedherein.

In accordance with embodiments of the invention, the system 130 isintended to represent various forms of digital computers, such aslaptops, desktops, video recorders, audio/video player, radio,workstations, servers, wearable devices, Internet-of-things devices,electronic kiosk devices (e.g., automated teller machine devices), bladeservers, mainframes, or any combination of the aforementioned. Inaccordance with embodiments of the invention, the user input device 140is intended to represent various forms of mobile devices, such aspersonal digital assistants, cellular telephones, smartphones, augmentedreality (AR) devices, virtual reality (VR) devices, extended reality(XR) devices, and other similar computing devices. The components shownhere, their connections and relationships, and their functions, aremeant to be exemplary only, and are not meant to limit implementationsof the inventions described and/or claimed in this document.

In accordance with some embodiments, the system 130 may include aprocessor 102, memory 104, a storage device 106, a high-speed interface108 connecting to memory 104, and a low-speed interface 112 connectingto low speed bus 114 and storage device 106. Each of the components 102,104, 106, 108, 111, and 112 are interconnected using various buses, andmay be mounted on a common motherboard or in other manners asappropriate. The processor 102 can process instructions for executionwithin the system 130, including instructions stored in the memory 104or on the storage device 106 as part of an application that may performthe functions disclosed herein, display graphical information for a GUIon an external input/output device, such as display 116 coupled to ahigh-speed interface 108, and/or the like. In other implementations,multiple processors and/or multiple buses may be used, as appropriate,along with multiple memories and types of memory. Also, multiplesystems, same or similar to system 130 may be connected, with eachsystem providing portions of the necessary operations (e.g., as a serverbank, a group of blade servers, or a multi-processor system). In someembodiments, the system 130 may be a server managed by the business. Thesystem 130 may be located at the facility associated with the businessor remotely from the facility associated with the business.

The memory 104 stores information within the system 130. In oneimplementation, the memory 104 is a volatile memory unit or units, suchas volatile random access memory (RAM) having a cache area for thetemporary storage of information. In another implementation, the memory104 is a non-volatile memory unit or units. The memory 104 may also beanother form of computer-readable medium, such as a magnetic or opticaldisk, which may be embedded and/or may be removable. The non-volatilememory may additionally or alternatively include an EEPROM, flashmemory, and/or the like. The memory 104 may store any one or more ofpieces of information and data used by the system in which it resides toimplement the functions of that system. In this regard, the system maydynamically utilize the volatile memory over the non-volatile memory bystoring multiple pieces of information in the volatile memory, therebyreducing the load on the system and increasing the processing speed.

The storage device 106 is capable of providing mass storage for thesystem 130. In one aspect, the storage device 106 may be or contain acomputer-readable medium, such as a floppy disk device, a hard diskdevice, an optical disk device, or a tape device, a flash memory orother similar solid state memory device, or an array of devices,including devices in a storage area network or other configurations. Acomputer program product can be tangibly embodied in an informationcarrier. The computer program product may also contain instructionsthat, when executed, perform one or more methods, such as thosedescribed above. The information carrier may be a non-transitorycomputer- or machine-readable storage medium, such as the memory 104,the storage device 104, or memory on processor 102.

In some embodiments, the system 130 may be configured to access, via thenetwork 110, a number of other computing devices (not shown) in additionto the user input device 140. In this regard, the system 130 may beconfigured to access one or more storage devices and/or one or morememory devices associated with each of the other computing devices. Inthis way, the system 130 may implement dynamic allocation andde-allocation of local memory resources among multiple computing devicesin a parallel or distributed system. Given a group of computing devicesand a collection of interconnected local memory devices, thefragmentation of memory resources is rendered irrelevant by configuringthe system 130 to dynamically allocate memory based on availability ofmemory either locally, or in any of the other computing devicesaccessible via the network. In effect, it appears as though the memoryis being allocated from a central pool of memory, even though the spaceis distributed throughout the system. This method of dynamicallyallocating memory provides increased flexibility when the data sizechanges and allows memory reuse for better utilization of the memoryresources when the data sizes are large.

The high-speed interface 108 manages bandwidth-intensive operations forthe system 130, while the low speed controller 112 manages lowerbandwidth-intensive operations. Such allocation of functions isexemplary only. In some embodiments, the high-speed interface 108 iscoupled to memory 104, display 116 (e.g., through a graphics processoror accelerator), and to high-speed expansion ports 111, which may acceptvarious expansion cards (not shown). In such an implementation,low-speed controller 112 is coupled to storage device 106 and low-speedexpansion port 114. The low-speed expansion port 114, which may includevarious communication ports (e.g., USB, Bluetooth, Ethernet, wirelessEthernet), may be coupled to one or more input/output devices, such as akeyboard, a pointing device, a scanner, or a networking device such as aswitch or router, e.g., through a network adapter.

The system 130 may be implemented in a number of different forms, asshown in FIG. 1 . For example, it may be implemented as a standardserver, or multiple times in a group of such servers. Additionally, thesystem 130 may also be implemented as part of a rack server system or apersonal computer such as a laptop computer. Alternatively, componentsfrom system 130 may be combined with one or more other same or similarsystems and an entire system 130 may be made up of multiple computingdevices communicating with each other.

FIG. 1 also illustrates a user input device 140, in accordance with anembodiment of the invention. The user input device 140 includes aprocessor 152, memory 154, an input/output device such as a display 156,a communication interface 158, and a transceiver 160, among othercomponents. The user input device 140 may also be provided with astorage device, such as a microdrive or other device, to provideadditional storage. Each of the components 152, 154, 158, and 160, areinterconnected using various buses, and several of the components may bemounted on a common motherboard or in other manners as appropriate.

The processor 152 is configured to execute instructions within the userinput device 140, including instructions stored in the memory 154, whichin one embodiment includes the instructions of an application that mayperform the functions disclosed herein. The processor may be implementedas a chipset of chips that include separate and multiple analog anddigital processors. The processor may be configured to provide, forexample, for coordination of the other components of the user inputdevice 140, such as control of user interfaces, applications run by userinput device 140, and wireless communication by user input device 140.

The processor 152 may be configured to communicate with the user throughcontrol interface 164 and display interface 166 coupled to a display156. The display 156 may be, for example, a TFT LCD(Thin-Film-Transistor Liquid Crystal Display) or an OLED (Organic LightEmitting Diode) display, or other appropriate display technology. Thedisplay interface 156 may comprise appropriate circuitry and configuredfor driving the display 156 to present graphical and other informationto a user. The control interface 164 may receive commands from a userand convert them for submission to the processor 152. In addition, anexternal interface 168 may be provided in communication with processor152, so as to enable near area communication of user input device 140with other devices. External interface 168 may provide, for example, forwired communication in some implementations, or for wirelesscommunication in other implementations, and multiple interfaces may alsobe used.

The memory 154 stores information within the user input device 140. Thememory 154 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory may also be provided andconnected to user input device 140 through an expansion interface (notshown), which may include, for example, a SIMM (Single In Line MemoryModule) card interface. Such expansion memory may provide extra storagespace for user input device 140 or may also store applications or otherinformation therein. In some embodiments, expansion memory may includeinstructions to carry out or supplement the processes described aboveand may include secure information also. For example, expansion memorymay be provided as a security module for user input device 140 and maybe programmed with instructions that permit secure use of user inputdevice 140. In addition, secure applications may be provided via theSIMM cards, along with additional information, such as placingidentifying information on the SIMM card in a non-hackable manner. Insome embodiments, the user may use the applications to execute processesdescribed with respect to the process flows described herein.Specifically, the application executes the process flows describedherein.

The memory 154 may include, for example, flash memory and/or NVRAMmemory. In one aspect, a computer program product is tangibly embodiedin an information carrier. The computer program product containsinstructions that, when executed, perform one or more methods, such asthose described herein. The information carrier is a computer—ormachine-readable medium, such as the memory 154, expansion memory,memory on processor 152, or a propagated signal that may be received,for example, over transceiver 160 or external interface 168.

In some embodiments, the user may use the user input device 140 totransmit and/or receive information or commands to and from the system130 via the network 110. Any communication between the system 130 andthe user input device 140 (or any other computing devices) may besubject to an authentication protocol allowing the system 130 tomaintain security by permitting only authenticated users (or processes)to access the protected resources of the system 130, which may includeservers, databases, applications, and/or any of the components describedherein. To this end, the system 130 may require the user (or process) toprovide authentication credentials to determine whether the user (orprocess) is eligible to access the protected resources. Once theauthentication credentials are validated and the user (or process) isauthenticated, the system 130 may provide the user (or process) withpermissioned access to the protected resources. Similarly, the userinput device 140 (or any other computing devices) may provide the system130 with permissioned to access the protected resources of the userinput device 130 (or any other computing devices), which may include aGPS device, an image capturing component (e.g., camera), a microphone, aspeaker, and/or any of the components described herein.

The user input device 140 may communicate with the system 130 (and oneor more other devices) wirelessly through communication interface 158,which may include digital signal processing circuitry where necessary.Communication interface 158 may provide for communications under variousmodes or protocols, such as GSM voice calls, SMS, EMS, or MMS messaging,CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others. Suchcommunication may occur, for example, through radio-frequencytransceiver 160. In addition, short-range communication may occur, suchas using a Bluetooth, Wi-Fi, or other such transceiver (not shown). Inaddition, GPS (Global Positioning System) receiver module 170 mayprovide additional navigation—and location-related wireless data to userinput device 140, which may be used as appropriate by applicationsrunning thereon, and in some embodiments, one or more applicationsoperating on the system 130.

The user input device 140 may also communicate audibly using audio codec162, which may receive spoken information from a user and convert it tousable digital information. Audio codec 162 may likewise generateaudible sound for a user, such as through a speaker, e.g., in a handsetof user input device 140. Such sound may include sound from voicetelephone calls, may include recorded sound (e.g., voice messages, musicfiles, etc.) and may also include sound generated by one or moreapplications operating on the user input device 140, and in someembodiments, one or more applications operating on the system 130.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in atechnical environment that includes a back end component (e.g., as adata server), that includes a middleware component (e.g., an applicationserver), that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components.

As shown in FIG. 1 , the components of the system 130 and the user inputdevice 140 are interconnected using the network 110. The network 110,which may be include one or more separate networks, be a form of digitalcommunication network such as a telecommunication network, a local areanetwork (“LAN”), a wide area network (“WAN”), a global area network(“GAN”), the Internet, or any combination of the foregoing. It will alsobe understood that the network 110 may be secure and/or unsecure and mayalso include wireless and/or wired and/or optical interconnectiontechnology.

In accordance with an embodiments of the invention, the components ofthe system environment 100, such as the system 130 and the user inputdevice 140 may have a client-server relationship, where the user inputdevice 130 makes a service request to the system 130, the system 130accepts the service request, processes the service request, and returnsthe requested information to the user input device 140, and vice versa.This relationship of client and server typically arises by virtue ofcomputer programs running on the respective computers and having aclient-server relationship to each other.

It will be understood that the embodiment of the system environment 100illustrated in FIG. 1 is exemplary and that other embodiments may vary.As another example, in some embodiments, the system environment mayinclude more, fewer, or different components. As another example, insome embodiments, some or all of the portions of the system environment100 may be combined into a single portion. Likewise, in someembodiments, some, or all of the portions of the system 130 may beseparated into two or more distinct portions.

Vulnerability testing is an assessment used to evaluate applicationsecurity by identifying, diagnosing, and triaging applicationvulnerabilities. Vulnerability testing tools are useful for testing forknown vulnerabilities. Typically, most entities employ some form ofthird party vulnerability testing tools to protect their technologyinfrastructure. These include, static application security analysis,dynamic application security analysis, penetration testing, imagescanners, configuration reviews, and/or the like. However, in caseswhere a previously unseen vulnerability is to be identified across thetechnology infrastructure, the capabilities of these third party toolsmay be limited.

There present invention provides the functional benefit of quicklydeploying a platform agnostic targeted software vulnerability testing(SVT) engine that can identify components (e.g., software libraries,applications, or the like) that are affected by the specificvulnerabilities.

FIG. 2 illustrates a process flow for deployable software vulnerabilitytesting platform 200, in accordance with an embodiment of the invention.As shown in block 202, the process flow includes receiving, from a userinput device, an initial request from a user to generate a deployablesoftware vulnerability testing (SVT) engine to identify one or moreinstances of a first vulnerability within a distributed technologyinfrastructure (e.g., operating system, open ports, installed software,user accounts, file system structure, system configurations, and more).In some embodiments, the first vulnerability may be a software code flawor a system misconfiguration through which malicious actors can directlygain unauthorized access to a system or network. Once inside, thesemalicious actors can leverage authorizations and privileges tocompromise systems and resources. In some other embodiments, the firstvulnerability may be a means through which malicious actors use avulnerability to mount a misappropriate action. In such cases, the firstvulnerability may be a piece of specially crafted software or a sequenceof commands. In some other embodiments, the first vulnerability may be aset of conditions that are present for a potential misappropriateaction. Examples of vulnerabilities include broken authentication, codeinjection, cross-site scripting, security misconfiguration, and/or thelike.

Next, as shown in block 204, the process flow includes prompting an SVTdashboard for display on the user input device to receive one or moreinput parameters associated with the first vulnerability in response toreceiving the initial request. Next, as shown in block 206, the processflow includes receiving, via the SVT dashboard, the one or more inputparameters. In some embodiments, the one or more input parameters mayinclude vulnerability identification vectors (e.g., vulnerabilitysignatures) that are used to identify a particular vulnerability. In oneaspect, the one or more input parameters may include a formalizedrepresentation (e.g., regular expression) of the vulnerability language.In other words, the input parameters may include information associatedwith the first vulnerability, such as known vulnerability signaturesassociated with the first vulnerability.

Next, as shown in block 208, the process flow includes generating theSVT engine based on at least the one or more input parameters. In someembodiments, the SVT engine may be self-contained, butexternally-controllable code that encapsulates powerful logic designedto perform or execute instructions to scan the distributed technologyinfrastructure, including operating systems, open ports, installedsoftware, user accounts, file system structure, system configurations,and/or the like to identify the first vulnerability. As describedherein, the SVT engine may be platform agnostic, i.e., capable ofrunning on any combination or operating system and underlying processorarchitecture.

Next, as shown in block 210, the process flow includes receiving, fromthe user input device, one or more deployment parameters associated witha deployment of the SVT engine. Next, as shown in block 212, the processflow includes deploying the SVT engine within the distributed technologyinfrastructure to identify the one or more instances of the firstvulnerability based on at least the one or more deployment parameters.

In some embodiments, the deployment parameters may specify a first setof applications within the distributed technology infrastructure for theSVT engine to be deployed to identify instances of the firstvulnerability. In this regard, the system may be configured to receiveinformation associated a first set of applications. In one aspect, theinformation associated with the first set of applications may include atleast an application version. In response, the system may be configuredto deploy the SVT engine to identify the one or more instances of thefirst vulnerability within the first set of applications within thedistributed technology infrastructure.

In some embodiments, the deployment parameters may specify particularsoftware libraries within the distributed technology infrastructure forthe SVT engine to be deployed to identify instances of the firstvulnerability. In this regard, the system may be configured to receiveinformation associated with one or more software libraries. In response,the system may be configured to determine a second set of applicationsthat are associated with the one or more software libraries. Havingdetermined the second set of applications, the system may be configuredto deploy the SVT engine to identify instances of the firstvulnerability within the second set of applications within thedistributed technology infrastructure.

In some embodiments, the system may be configured to receive, from theuser input device, a number of mitigation actions to be executed inresponse to identifying specific vulnerabilities. These actions are thenstored in a repository and accessible when necessary. In someembodiments, these actions may include a software patch that isconfigured to address the identified vulnerability in all the identifiedinstances. Accordingly, the system may be configured to identify the oneor more instances of the first vulnerability within the distributedtechnology infrastructure based on at least deploying the SVT enginewithin the distributed technology infrastructure. In response, thesystem may be configured to automatically retrieve, from the actionrepository, the one or more actions in response to identifying the oneor more instances of the first vulnerability. Once retrieved, the systemmay be configured to execute the one or more actions on the firstvulnerability in the one or more instances identified.

As will be appreciated by one of ordinary skill in the art in view ofthis disclosure, the present invention may include and/or be embodied asan apparatus (including, for example, a system, machine, device,computer program product, and/or the like), as a method (including, forexample, a business method, computer-implemented process, and/or thelike), or as any combination of the foregoing. Accordingly, embodimentsof the present invention may take the form of an entirely businessmethod embodiment, an entirely software embodiment (including firmware,resident software, micro-code, stored procedures in a database, or thelike), an entirely hardware embodiment, or an embodiment combiningbusiness method, software, and hardware aspects that may generally bereferred to herein as a “system.” Furthermore, embodiments of thepresent invention may take the form of a computer program product thatincludes a computer-readable storage medium having one or morecomputer-executable program code portions stored therein. As usedherein, a processor, which may include one or more processors, may be“configured to” perform a certain function in a variety of ways,including, for example, by having one or more general-purpose circuitsperform the function by executing one or more computer-executableprogram code portions embodied in a computer-readable medium, and/or byhaving one or more application-specific circuits perform the function.

It will be understood that any suitable computer-readable medium may beutilized. The computer-readable medium may include, but is not limitedto, a non-transitory computer-readable medium, such as a tangibleelectronic, magnetic, optical, electromagnetic, infrared, and/orsemiconductor system, device, and/or other apparatus. For example, insome embodiments, the non-transitory computer-readable medium includes atangible medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), and/or some other tangible optical and/ormagnetic storage device. In other embodiments of the present invention,however, the computer-readable medium may be transitory, such as, forexample, a propagation signal including computer-executable program codeportions embodied therein.

One or more computer-executable program code portions for carrying outoperations of the present invention may include object-oriented,scripted, and/or unscripted programming languages, such as, for example,Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, JavaScript,and/or the like. In some embodiments, the one or morecomputer-executable program code portions for carrying out operations ofembodiments of the present invention are written in conventionalprocedural programming languages, such as the “C” programming languagesand/or similar programming languages. The computer program code mayalternatively or additionally be written in one or more multi-paradigmprogramming languages, such as, for example, F #.

Some embodiments of the present invention are described herein withreference to flowchart illustrations and/or block diagrams of apparatusand/or methods. It will be understood that each block included in theflowchart illustrations and/or block diagrams, and/or combinations ofblocks included in the flowchart illustrations and/or block diagrams,may be implemented by one or more computer-executable program codeportions. These one or more computer-executable program code portionsmay be provided to a processor of a general purpose computer, specialpurpose computer, and/or some other programmable data processingapparatus in order to produce a particular machine, such that the one ormore computer-executable program code portions, which execute via theprocessor of the computer and/or other programmable data processingapparatus, create mechanisms for implementing the steps and/or functionsrepresented by the flowchart(s) and/or block diagram block(s).

The one or more computer-executable program code portions may be storedin a transitory and/or non-transitory computer-readable medium (e.g. amemory) that can direct, instruct, and/or cause a computer and/or otherprogrammable data processing apparatus to function in a particularmanner, such that the computer-executable program code portions storedin the computer-readable medium produce an article of manufactureincluding instruction mechanisms which implement the steps and/orfunctions specified in the flowchart(s) and/or block diagram block(s).

The one or more computer-executable program code portions may also beloaded onto a computer and/or other programmable data processingapparatus to cause a series of operational steps to be performed on thecomputer and/or other programmable apparatus. In some embodiments, thisproduces a computer-implemented process such that the one or morecomputer-executable program code portions which execute on the computerand/or other programmable apparatus provide operational steps toimplement the steps specified in the flowchart(s) and/or the functionsspecified in the block diagram block(s). Alternatively,computer-implemented steps may be combined with, and/or replaced with,operator- and/or human-implemented steps in order to carry out anembodiment of the present invention.

Although many embodiments of the present invention have just beendescribed above, the present invention may be embodied in many differentforms and should not be construed as limited to the embodiments setforth herein; rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. Also, it will beunderstood that, where possible, any of the advantages, features,functions, devices, and/or operational aspects of any of the embodimentsof the present invention described and/or contemplated herein may beincluded in any of the other embodiments of the present inventiondescribed and/or contemplated herein, and/or vice versa. In addition,where possible, any terms expressed in the singular form herein aremeant to also include the plural form and/or vice versa, unlessexplicitly stated otherwise. Accordingly, the terms “a” and/or “an”shall mean “one or more,” even though the phrase “one or more” is alsoused herein. Like numbers refer to like elements throughout.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations, modifications, andcombinations of the just described embodiments can be configured withoutdeparting from the scope and spirit of the invention. Therefore, it isto be understood that, within the scope of the appended claims, theinvention may be practiced other than as specifically described herein.

What is claimed is:
 1. A system for deployable software vulnerability testing platform, the system comprising: at least one non-transitory storage device; and at least one processor coupled to the at least one non-transitory storage device, wherein the at least one processor is configured to: receive, from a user input device, an initial request from a user to generate a deployable software vulnerability testing (SVT) engine to identify one or more instances of a first vulnerability within a distributed technology infrastructure; prompt an SVT dashboard for display on the user input device to receive one or more input parameters associated with the first vulnerability in response to receiving the initial request; receive, via the SVT dashboard, the one or more input parameters; generate the SVT engine based on at least the one or more input parameters; receive, from the user input device, one or more deployment parameters associated with a deployment of the SVT engine; and deploy the SVT engine within the distributed technology infrastructure to identify the one or more instances of the first vulnerability based on at least the one or more deployment parameters.
 2. The system of claim 1, wherein the SVT engine is platform agnostic.
 3. The system of claim 1, wherein the at least one processor is further configured to: receive, via the SVT dashboard, the one or more deployment parameters, wherein the one or more deployment parameters comprises at least information associated a first set of applications within the distributed technology infrastructure; and deploy the SVT engine to identify the one or more instances of the first vulnerability within the first set of applications within the distributed technology infrastructure.
 4. The system of claim 3, wherein the information associated with the first set of applications comprises at least an application version.
 5. The system of claim 1, wherein the at least one processor is further configured to: receive, via the SVT dashboard, the one or more deployment parameters, wherein the one or more deployment parameters comprises at least information associated with one or more software libraries; determine a second set of applications that are associated with the one or more software libraries; and deploy the SVT engine to identify the one or more instances of the first vulnerability within the second set of applications within the distributed technology infrastructure.
 6. The system of claim 1, wherein the one or more input parameters comprises at least information associated with the first vulnerability, wherein the information comprises at least one or more known vulnerability signatures associated with the first vulnerability.
 7. The system of claim 1, wherein the at least one processor is further configured to: receive, from the user input device, one or more actions to be executed in response to identifying the one or more instances of the first vulnerability within the distributed technology infrastructure; and store the one or more actions in an action repository.
 8. The system of claim 7, wherein the one or more actions comprises at least a software patch configured to address the first vulnerability in the one or more instances identified.
 9. The system of claim 7, wherein the at least one processor is further configured to: identify the one or more instances of the first vulnerability within the distributed technology infrastructure based on at least deploying the SVT engine within the distributed technology infrastructure; automatically retrieve, from the action repository, the one or more actions in response to identifying the one or more instances of the first vulnerability; and executing the one or more actions on the first vulnerability in the one or more instances identified.
 10. A computer program product for deployable software vulnerability testing platform, the computer program product comprising a non-transitory computer-readable medium comprising code causing a first apparatus to: receive, from a user input device, an initial request from a user to generate a deployable software vulnerability testing (SVT) engine to identify one or more instances of a first vulnerability within a distributed technology infrastructure; prompt an SVT dashboard for display on the user input device to receive one or more input parameters associated with the first vulnerability in response to receiving the initial request; receive, via the SVT dashboard, the one or more input parameters; generate the SVT engine based on at least the one or more input parameters; receive, from the user input device, one or more deployment parameters associated with a deployment of the SVT engine; and deploy the SVT engine within the distributed technology infrastructure to identify the one or more instances of the first vulnerability based on at least the one or more deployment parameters.
 11. The computer program product of claim 10, wherein the SVT engine is platform agnostic.
 12. The computer program product of claim 10, wherein the first apparatus is further configured to: receive, via the SVT dashboard, the one or more deployment parameters, wherein the one or more deployment parameters comprises at least information associated a first set of applications within the distributed technology infrastructure; and deploy the SVT engine to identify the one or more instances of the first vulnerability within the first set of applications within the distributed technology infrastructure.
 13. The computer program product of claim 12, wherein the information associated with the first set of applications comprises at least an application version.
 14. The computer program product of claim 10, wherein the first apparatus is further configured to: receive, via the SVT dashboard, the one or more deployment parameters, wherein the one or more deployment parameters comprises at least information associated with one or more software libraries; determine a second set of applications that are associated with the one or more software libraries; and deploy the SVT engine to identify the one or more instances of the first vulnerability within the second set of applications within the distributed technology infrastructure.
 15. The computer program product of claim 10, wherein the one or more input parameters comprises at least information associated with the first vulnerability, wherein the information comprises at least one or more known vulnerability signatures associated with the first vulnerability.
 16. The computer program product of claim 10, wherein the first apparatus is further configured to: receive, from the user input device, one or more actions to be executed in response to identifying the one or more instances of the first vulnerability within the distributed technology infrastructure; and store the one or more actions in an action repository.
 17. The computer program product of claim 16, wherein the one or more actions comprises at least a software patch configured to address the first vulnerability in the one or more instances identified.
 18. The computer program product of claim 16, wherein the first apparatus is further configured to: identify the one or more instances of the first vulnerability within the distributed technology infrastructure based on at least deploying the SVT engine within the distributed technology infrastructure; automatically retrieve, from the action repository, the one or more actions in response to identifying the one or more instances of the first vulnerability; and executing the one or more actions on the first vulnerability in the one or more instances identified.
 19. A method for deployable software vulnerability testing platform, the method comprising: receiving, from a user input device, an initial request from a user to generate a deployable software vulnerability testing (SVT) engine to identify one or more instances of a first vulnerability within a distributed technology infrastructure; prompting an SVT dashboard for display on the user input device to receive one or more input parameters associated with the first vulnerability in response to receiving the initial request; receiving, via the SVT dashboard, the one or more input parameters; generating the SVT engine based on at least the one or more input parameters; receiving, from the user input device, one or more deployment parameters associated with a deployment of the SVT engine; and deploying the SVT engine within the distributed technology infrastructure to identify the one or more instances of the first vulnerability based on at least the one or more deployment parameters.
 20. The method of claim 19, wherein the SVT engine is platform agnostic. 